[breaking change detector] Add 'six' to development requirements#46774
Closed
[breaking change detector] Add 'six' to development requirements#46774
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the breaking change detector’s development requirements to include six, ensuring the checker’s venv setup can install an additional Python dependency during execution.
Changes:
- Add
sixtoscripts/breaking_changes_checker/dev_requirements.txt.
Comment on lines
1
to
+3
| -e ../../eng/tools/azure-sdk-tools | ||
| jsondiff>=1.2.0 | ||
| six |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines